‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- candidate test file ---'
cat -n test/site.mjs | sed -n '1,90p'

printf '%s\n' '--- Node.js target declarations ---'
rg -n --hidden --glob '!node_modules' --glob '!dist' --glob '!build' \
  '"(engines|node)"|node-version|NODE_VERSION|Node\.js|nodejs' \
  package.json package-lock.json npm-shrinkwrap.json .nvmrc .node-version \
  .github README.md 2>/dev/null || true

printf '%s\n' '--- requestWithHost usages ---'
rg -n --hidden --glob '!node_modules' 'requestWithHost|setTimeout|setTimeouts|timeout|aborted|res\.once\("error"|res\.on\("error"' .

Repository: gitcommit90/1Helm

Length of output: 50373

🏁 Script executed:

#!/bin/bash
set -eu

printf '%s\n' '--- project manifest ---'
python3 - <<'PY'
import json
with open("package.json") as f:
    package = json.load(f)
print(json.dumps({
    "engines": package.get("engines"),
    "scripts": package.get("scripts"),
    "dependencies": package.get("dependencies"),
    "devDependencies": package.get("devDependencies"),
}, indent=2))
PY

printf '%s\n' '--- CI runtime selection ---'
cat -n .github/workflows/ci.yml | sed -n '15,32p'

printf '%s\n' '--- focused timeout patterns ---'
rg -n -C 2 --hidden --glob '!node_modules' --glob '!package-lock.json' \
  'request\(|\.setTimeout\(|timeout\s*:' test scripts site .github package.json 2>/dev/null | head -200

printf '%s\n' '--- available local Node runtime ---'
node --version
node -e 'const {request}=require("node:http"); const req=request({hostname:"127.0.0.1",port:1}); console.log({requestSetTimeout:typeof req.setTimeout, requestSetTimeoutArity:req.setTimeout.length}); req.destroy();'

Repository: gitcommit90/1Helm

Length of output: 24737

🌐 Web query:

Node.js 22 http.ClientRequest setTimeout IncomingMessage aborted error official documentation

💡 Result:

In Node.js 22, the http.ClientRequest timeout behavior and IncomingMessage error handling are defined as follows: 1. http.ClientRequest setTimeout: When you use request.setTimeout(timeout[, callback]) on an http.ClientRequest, it sets a timeout on the underlying socket once it is assigned and connected [1][2]. The 'timeout' event is emitted when the socket experiences inactivity for the specified duration [1][2]. Crucially, this event only notifies you that the socket has been idle; it does not automatically destroy the request [1][2]. You must manually destroy the request (e.g., by calling request.destroy or request.abort) inside the 'timeout' event handler if you wish to terminate it [1][2]. If no 'timeout' listener is added to the request, response, or server, Node.js will automatically destroy the socket when it times out [2]. 2. IncomingMessage 'aborted' error: The 'aborted' event on IncomingMessage is deprecated [3]. Official documentation advises developers to listen for the 'close' event instead [3]. However, there is significant community discussion and known difficulty regarding this transition, as 'close' is emitted under various conditions (including when a request completes normally) [4][3], whereas 'aborted' specifically indicated a premature termination [4]. To accurately detect an abort in modern Node.js versions, some developers check the readableEnded property on the request/response object within the 'close' event handler to determine if the stream ended prematurely [4]. Node.js does not reliably emit an 'error' event specifically for client-side aborts unless manually handled in the application logic [5].

Citations:

• 1: https://nodejs.org/docs/v22.14.0/api/http.html
• 2: https://github.com/nodejs/node/blob/master/doc/api/http.md
• 3: Detecting client request aborts in nodejs >= 15.50 is broken nodejs/node#46666
• 4: http.IncomingMessage aborted Event isn't the same as http.IncomingMessage close Event nodejs/node#43688
• 5: http: 'aborted' IncomingMessage should 'error' nodejs/node#33172

🏁 Script executed:

#!/bin/bash
set -eu

node <<'JS'
const http = require("node:http");
const { EventEmitter } = require("node:events");
const { Readable } = require("node:stream");

const req = http.request({ host: "127.0.0.1", port: 1 });
const result = {
  node: process.version,
  clientRequestSetTimeout: typeof req.setTimeout,
  clientRequestDestroy: typeof req.destroy,
  readableSetTimeout: typeof Readable.prototype.setTimeout,
  eventEmitterMethods: {
    on: typeof EventEmitter.prototype.on,
    once: typeof EventEmitter.prototype.once,
  },
};
req.once("error", () => {});
req.destroy();
console.log(JSON.stringify(result, null, 2));
JS

printf '%s\n' '--- exact CI Node declarations ---'
rg -n -C 2 'node-version|setup-node|engines' .github package.json | head -80

Repository: gitcommit90/1Helm

Length of output: 771

🌐 Web query:

site:nodejs.org/docs/v22.14.0/api/http.html IncomingMessage message.setTimeout ClientRequest setTimeout aborted close

💡 Result:

In Node.js, the timeout behaviors for HTTP objects are distinct between ClientRequest and IncomingMessage. ClientRequest represents the request made by a client. It provides a request.setTimeout(timeout[, callback]) method which, once a socket is assigned and connected, calls socket.setTimeout on the underlying socket [1]. The 'timeout' event is emitted when the underlying socket times out from inactivity; notably, this event only notifies that the socket has been idle, and the request must be destroyed manually by the developer [1]. IncomingMessage represents the response object received by the client (or the request object received by a server). While the http.ServerResponse and some socket-based streams may support specific timeout methods, IncomingMessage itself does not provide a general message.setTimeout method in the documented HTTP API [1]. If you are encountering errors involving aborted or close events in relation to timeouts, they typically follow this lifecycle: 1. Timeout Trigger: The socket times out due to inactivity [1]. 2. Manual Intervention: Because the timeout event only notifies of idleness, you must explicitly call request.destroy or request.abort to close the connection [1]. 3. Event Emission: Once destroyed or aborted, the 'abort' and 'close' events are emitted on the request object [1]. If you are observing unexpected 'aborted' or 'close' behavior, ensure your code explicitly handles the 'timeout' event by destroying the request if the default idle timeout behavior is not desired [1].

Citations:

• 1: https://nodejs.org/docs/v22.14.0/api/http.html

🏁 Script executed:

#!/bin/bash
set -eu

node <<'JS'
const http = require("node:http");
const { EventEmitter } = require("node:events");

const req = http.request({ host: "127.0.0.1", port: 1 });
const incoming = http.IncomingMessage.prototype;
const result = {
  node: process.version,
  clientRequest: {
    setTimeout: typeof req.setTimeout,
    destroy: typeof req.destroy,
  },
  incomingMessage: {
    setTimeout: typeof incoming.setTimeout,
    destroy: typeof incoming.destroy,
    on: typeof incoming.on,
    once: typeof incoming.once,
    abortedDescriptor: Object.getOwnPropertyDescriptor(incoming, "aborted") !== undefined,
  },
  eventEmitter: {
    on: typeof EventEmitter.prototype.on,
    once: typeof EventEmitter.prototype.once,
  },
};
req.once("error", () => {});
req.destroy();
console.log(JSON.stringify(result, null, 2));
JS

Repository: gitcommit90/1Helm

Length of output: 494

🌐 Web query:

Node.js v22.14.0 http IncomingMessage.prototype.setTimeout source message.setTimeout

💡 Result:

In Node.js v22.14.0, the message.setTimeout method is a member of the http.IncomingMessage prototype [1][2]. Its primary function is to set a timeout value on the underlying socket associated with the incoming message [3][4]. Method Definition The method signature is message.setTimeout(msecs[, callback]) [4]. It accepts two arguments: msecs (number): The number of milliseconds to wait before the socket times out. callback (function, optional): An optional listener to be called when a timeout occurs [4]. Implementation Details Internally, the method is defined in the Node.js source code (typically lib/_http_incoming.js) as follows [3][5]: IncomingMessage.prototype.setTimeout = function setTimeout(msecs, callback) { if (callback) this.on('timeout', callback); this.socket.setTimeout(msecs); return this; }; Behavioral Notes 1. Socket Delegation: The method calls the setTimeout method of the underlying message.socket [6][4]. 2. Return Value: It returns the IncomingMessage instance itself, allowing for method chaining [7]. 3. Callback Handling: While the implementation adds the callback as a listener for the 'timeout' event on the IncomingMessage instance, historical issues have noted that because IncomingMessage does not always emit 'timeout' directly, reliance on the callback via this specific method has been a point of technical discussion [3]. Users are often advised to interact directly with the socket's timeout mechanisms if precise control is required [3]. Documentation for this method can be found in the official Node.js HTTP module documentation under the IncomingMessage class section [1][2].

Citations:

• 1: https://nodejs.org/docs/v22.14.0/api/http.html
• 2: https://nodejs.org/download/release/v22.14.0/docs/api/http.html
• 3: http.IncomingMessage doesn't fire callback on 'timeout' nodejs/node#33734
• 4: https://nodejs.cn/api/http/message_settimeout_msecs_callback.html
• 5: https://www.neversaw.us/scratch/node-coverage/lib/_http_incoming.js.html
• 6: https://bun.com/reference/node/http/IncomingMessage/setTimeout
• 7: jrasanen/node@d4726cd

🏁 Script executed:

#!/bin/bash
set -eu
printf '%s\n' '--- test/site.mjs context ---'
sed -n '45,75p' test/site.mjs
printf '%s\n' '--- related wording and assertions ---'
rg -n -C 2 'signed Setup executable|unsigned Setup executable|doesNotMatch|getttingStarted|gettingStarted' test .
printf '%s\n' '--- regex behavior ---'
python3 - <<'PY'
import re
pattern = re.compile(r"signed Setup executable", re.I)
bounded = re.compile(r"\bsigned Setup executable\b", re.I)
for text in ("signed Setup executable", "unsigned Setup executable"):
    print(repr(text), bool(pattern.search(text)), bool(bounded.search(text)))
PY

Repository: gitcommit90/1Helm

Length of output: 50373

🏁 Script executed:

#!/bin/bash
set -eu
node - <<'JS'
const broad = /signed Setup executable/i;
const bounded = /\bsigned Setup executable\b/i;
for (const text of ["signed Setup executable", "unsigned Setup executable"]) {
  console.log(JSON.stringify(text), {
    broad: broad.test(text),
    bounded: bounded.test(text),
  });
}
JS

Repository: gitcommit90/1Helm

Length of output: 272